What does this PR fix?

Fixes #1695, users were unable to delete clips in Studio Mode after pausing a camera-only recording.

Root cause

deleteClipSegment in context.ts had a guard that prevented deletion when fewer than 2 timeline segments shared the same recordingSegment index (i.e., the same pause interval).
This meant the "last" clip from any paused segment became permanently undeletable, even when other segments remained in the timeline.

The ConfigSidebar.tsx Delete button used the same incorrect condition to disable itself.

Additionally, the condition !segment.recordingSegment === undefined in the original guard was always false (boolean vs. undefined comparison) — dead code that never fired.

Changes

• context.ts: Updated deleteClipSegment guard — now only blocks deletion when it would leave the timeline completely empty (segments.length < 2), rather than blocking when it's the last clip of a specific recording segment.
• ConfigSidebar.tsx: Updated the Delete button disabled prop to use the same corrected logic.

Testing

1. Record with Camera Only enabled, pause and resume multiple times.
2. Open the recording in Studio Mode.
3. Select a clip from a paused segment and press Delete (or use the Delete button in the sidebar).
4. Verify all clips except the very last one can be deleted.

Greptile Summary

This PR fixes a bug where clips in a paused camera-only recording segment could not be deleted in Studio Mode. The root cause was a guard that blocked deletion whenever fewer than two clips shared the same recordingSegment index, and a dead-code condition (!segment.recordingSegment === undefined) that always evaluated to false.

• context.ts: The deleteClipSegment guard now only prevents deleting when one segment remains in the entire timeline (segments.length < 2), removing both the dead boolean-vs-undefined comparison and the per-recording-segment filter.
• ConfigSidebar.tsx: The Delete button's disabled prop is updated to match the new guard, ensuring UI state stays in sync with the action's actual behavior.

Confidence Score: 5/5

The change is safe to merge — it relaxes an overly strict guard and aligns the UI disabled state with the action logic.

Both modified sites (the action guard and the button disabled prop) are now consistent with each other and with the intended behavior: only the very last timeline segment is protected from deletion. The removed dead-code condition never fired, so its removal has no side effects.

No files require special attention.

Important Files Changed

_{Reviews (1): Last reviewed commit: "fix: allow deleting last clip per record..." | Re-trigger Greptile}